Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, so the description's claim of returning data is consistent. It adds context by specifying the returned items are 'live agent-ready' and from 'DaedalMap', but does not describe pagination, limits, or output structure beyond a list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences, front-loaded with the purpose ('Free discovery') and immediately specifying the return value. Every word contributes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool is simple (no parameters, no output schema, one sibling tool type), the description adequately covers the purpose. However, it could be improved by hinting at the relationship with get_pack (e.g., 'Use this to browse available packs, then get_pack to retrieve a specific pack').

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, so by baseline the description does not need to add parameter semantics. The description mentions 'Free discovery' which aligns with no inputs, but no additional value is needed beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Returns' and the resource 'list of live agent-ready data packs available on DaedalMap', distinguishing it from siblings like 'get_pack' (which likely retrieves a single pack) and 'query_dataset' (which queries dataset content).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Free discovery' implies a browse/search use case, but there is no explicit guidance on when to use this tool versus alternatives (get_pack, query_dataset). No 'when not to use' is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.