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

The description claims 'Read-shaped tools only (anything that buys, sells or writes refuses)', implying the tool is read-only in effect. However, the annotation sets readOnlyHint=false, contradicting this claim. It also does not disclose side effects, authentication requirements, or rate limits. The contradiction makes the description unreliable.

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 a long, run-on sentence with an incomplete clause ('the path that proved the —') and trailing context about a registry URL. It is not front-loaded with essential information and contains redundant phrasing. It fails to be concise or well-structured.

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?

There is no output schema, so the description must explain return values. It only vaguely mentions 'come back with the facts, the path that proved the —', which is incomplete and ambiguous. The description also lacks information about error handling, expected input examples, or any operational details necessary for correct invocation.

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 is an empty object with additionalProperties: true, meaning any parameters are allowed but none are defined. The description does not explain any expected input properties (e.g., subject, objective), leaving the agent to guess what arguments to pass. Schema description coverage is 100% only because there are no parameters; the description adds no semantic value.

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 states a general purpose: 'Investigate one subject against a stated objective by calling several of these tools in a searched order.' This conveys that it is an orchestrator tool, but it is vague about the exact verb and resource, and the sentence is cut off ('the path that proved the —'). It does not clearly distinguish from siblings other than being a meta-caller, which is not explicit.

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?

There is no explicit guidance on when to use this tool vs alternatives. It implies usage for multi-step investigation ('Investigate one subject'), but does not state when it is appropriate or when not to use it. No alternatives are mentioned, and the description does not provide context for selection.

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