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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false. The description adds useful behavioral context by confirming that no upload, score edit, credit spend, or plugin installation occurs, though it does not describe caching, rate limits, or response format.

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 tight sentences with the core purpose front-loaded. The second sentence efficiently rules out several potentially confusing side effects without wasting words.

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 read-only documentation lookup with one optional parameter and no output schema, the description is largely complete. It could say more about the return format, such as whether the guide is Markdown or plain text, but the essential behavior is clear.

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%, so the single topic parameter is already documented. The description restates the topic values and slightly expands 'operations' into 'operation parameters/limits', but does not add syntax or mapping details 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 uses a specific verb and resource: returns static ScoreStarling reference documentation for clearly named topics. It also distinguishes this documentation lookup from action-oriented siblings by stating it uploads nothing, edits no score, spends no credits, and does not install a plugin skill.

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 topics imply when to use the tool, but the description does not explicitly say when to choose it over related tools or when not to use it. The negative side-effect list helps avoid confusion, but usage guidance is mostly implied rather than stated.

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