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

With empty annotations, the description carries the full burden. It only says the tool 'returns' a playbook, with no mention of side effects, permissions, rate limits, or whether it is a read-only operation. No behavioral traits are disclosed beyond the basic function.

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 exactly two sentences, front-loaded with the essential alias information and no fluff. It is extremely concise and well-structured for the tiny amount of information it conveys.

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?

A tool with 43 parameters, no output schema, and empty annotations requires far more explanation. The description does not explain what the playbook contains, how to pick parameters, or what the response looks like. It is a stub that fails to give the agent enough context to use it correctly.

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 input schema has 43 parameters with only 33% schema description coverage, so the description should compensate but does not. It provides no information about how parameters affect the playbook output, which parameters are relevant, or how to construct a valid request. The one-line description adds no semantic value 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 clearly states the tool 'Returns the Wisely agent-payment playbook' and identifies itself as an alias for wisely_start_here. It adds a specific audience context ('MCP-only clients and registry probes'), which differentiates it somewhat from siblings like get_playbook, though not from wisely_start_here itself.

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 gives no explicit guidance on when to use this tool over alternatives. It only says 'Alias for wisely_start_here' and mentions a narrow use case, but does not explain when to prefer this over wisely_start_here, get_playbook, or other playbook-related tools.

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