MCP Tools List

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered structurally. The description adds useful non-schema context: the HTTP endpoint, MCP spec version, and a billing note that the endpoint is absent from the public credit manifest. It still omits payload size or caching characteristics for an open-world manifest call.

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?

Three short, front-loaded segments (what it is, group, endpoint, cost) with no filler. Each line carries distinct information an agent or billing layer can use.

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?

An output schema exists, so return values need not be described, and the parameter surface is empty. Combined with the annotations and cost/endpoint metadata, the definition gives enough to invoke it correctly; only the trigger condition for using it 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the empty schema is self-explanatory. Baseline 4 applies. The endpoint tag adds marginal clarity about how the call is dispatched.

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 the resource ('tool manifest for MCP clients') and cites an API spec, so an agent can guess it returns the catalogue of available tools. However, it never says explicitly that the response enumerates tool definitions/schemas, and 'auto-generated' is framing rather than purpose. Adequate but vague on the actual returned content.

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 indication of when an agent should call this versus any sibling tool (e.g. astroway_agent_tools or astroway_mcp_agent_pool_status), nor when not to call it. The cost line hints at a billing caveat but supplies no usage context.

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