Mencoro guide

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior. The description adds genuinely new context: no account data is touched and no sign-in is required, which tells the agent this is a safe public read with no auth prerequisites.

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?

Front-loaded with purpose, followed by a necessary topic inventory and the calling convention. The long topic list is dense but earns its place as a routing aid; there is little wasted prose.

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 single optional, well-documented parameter and no output schema, the description is complete: it says what the tool returns (guide content on the named topics), the calling convention, and the auth posture. Nothing an agent needs is missing.

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 coverage is 100% and the schema already documents both the enum values and the omit/'index' convention. The description's topic enumeration largely restates the enum and repeats the index workflow, adding only light framing about what each topic contains.

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?

States a specific verb (answer questions) and resource (the public Mencoro guide), and enumerates the exact subject matter covered. It is clearly distinguishable from the data-fetching siblings, which return account/project data rather than documentation.

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?

Explicitly prescribes the call pattern: omit the topic for the index, then call with the topic that answers the question. It also states the tool needs no account and works unauthenticated. It does not, however, acknowledge overlapping siblings such as get_metric_glossary or get_share_of_voice_formula, which also answer definitional questions.

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