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

With no annotations, the description carries the burden of disclosing behavior. It lists return contents but does not mention whether the operation is read-only, what happens if the trace_id is invalid, or any limitations (e.g., 'when the request was profiled' suggests profiling must be enabled). It provides some context but is not fully transparent.

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 single efficient sentence that front-loads the core purpose and enumerates the included components. It is slightly dense but contains no wasted words. A more structured list could improve scannability, but it is concise and informative.

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 tool with no output schema and a single parameter, the description lists the main expected content (queries, external calls, errors, breakdown) and notes a caveat ('when the request was profiled'). However, it does not specify the exact format, nesting, or error behavior, leaving some ambiguity for a potentially complex response.

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 parameter description 'Trace id from phpray_traces' provides a useful source reference. However, the tool description adds no additional semantics beyond the schema, and the schema description is minimal, so it meets the baseline without exceeding it.

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 specifies the tool's purpose: it returns full details of a single request including wall time split, queries, external calls, errors, and component breakdown. This distinguishes it from siblings like phpray_traces (which likely lists trace IDs) and phpray_components (which focuses on breakdown).

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?

Usage is implied by the phrase 'One request in full' and the parameter description 'Trace id from phpray_traces,' suggesting you first obtain a trace ID from the sibling tool. However, there is no explicit guidance on when to choose this over alternatives or when not to use it, so it relies on inference.

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