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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds context that the docs are 'scoped' and that the list includes fetch timing guidance, which goes beyond the structured fields. No contradiction.

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 entire description is one efficient sentence with no filler. The core action and scope are front-loaded, and the added fetch-timing guidance earns its place without bloating the text.

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 list tool with one optional boolean parameter and no output schema, the description adequately communicates what the tool returns (the documents and their fetch timing). While it doesn't detail the exact list structure, that is not critical given the annotations and simplicity. Minor gap: no mention of the sibling get tool.

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?

Schema description coverage is 100% and the parameter include_urls already has a clear description with default value. The tool description adds no extra parameter semantics, so the baseline of 3 applies.

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' and resource 'scoped Mana agent documents', and adds 'and when each should be fetched by an AI agent' which defines the tool's specific purpose. It naturally distinguishes itself from the sibling get_mana_agent_doc by being a list operation, not a fetch.

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 usage: an agent would use this to discover available docs and decide when to fetch them. It does not explicitly name the alternative or state when not to use it, but the context is clear enough for a list-vs-get sibling pair. No exclusions are given.

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