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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that it returns agendas and mentions the 'public' nature, but does not disclose whether authentication is needed (despite an apiKey parameter), possible pagination, rate limits, or any side effects. The read-only nature is implied by 'List' but not explicitly declared.

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 concise, consisting of a single sentence that front-loads the core action and resource. The additional detail about return content is relevant and earns its place. No unnecessary words or filler.

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?

For a simple list operation with two parameters and no output schema, the description provides the essential purpose and return overview, which is adequate but incomplete. It lacks parameter descriptions and usage context, but the tool is simple enough that the agent can partially infer from the schema names. The description is not as complete as it could be given the absence of annotations and output schema.

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 description coverage is 0%, so the description must compensate for the lack of parameter explanations. However, it does not mention orgSlug or apiKey at all, and only weakly alludes to the organization via 'for an organization'. The agent cannot derive parameter meaning from the description beyond what the parameter names already suggest.

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 'List', the resource 'public agendas', and the scope 'for an organization'. It also mentions the response content (provider, service, session counts), which helps distinguish it from other agenda tools like agendas_get or agendas_create. The purpose is unambiguous and well-defined.

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 description implies when to use this tool (when listing public agendas) but does not explicitly state exclusions or alternatives. It could mention that for a single agenda, agendas_get is appropriate, but such guidance is missing. The context is clear but not fully developed.

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