list_agencies

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

No annotations are present, so the description must carry the full behavioral burden. It hints at response fields ('CPD presence', 'schedule-executor flag') but does not clarify if the tool is read-only, filters, or returns a list. No disclosure of destructive potential or required auth.

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 short but not effectively concise; it uses unclear jargon without front-loading a clear verb and resource. The single sentence would be better replaced with a clearer explanation.

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 lack of output schema and simple parameter, the description should provide complete context. It fails to describe what the tool returns, how the parameter works, or how it differs from sibling tools like list_categories. Extremely incomplete.

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 schema has one optional parameter 'contains' with zero description coverage (0%). The tool description does not mention this parameter or explain its purpose, leaving the agent without guidance on how to use it.

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 'Agency dictionary with live CPD presence + schedule-executor flag' is vague and jargon-heavy. It does not clearly state that the tool lists agencies, and the terms 'CPD presence' and 'schedule-executor flag' are unexplained, making the purpose ambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like dataset_info or resolve_project_reference. The description lacks context for selecting this tool over siblings.

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