get_rpc_trace

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

No annotations are provided, so the description carries full behavioral burden, but it only specifies return content in vague terms. It does not state read-only behavior, side effects, required permissions, pagination semantics, or return shape, all of which matter for an evidence/trace tool.

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 sentence with no wasted words, but it is under-specified rather than concise. It front-loads the verb, yet the remainder is too abstract to earn its place for a tool requiring more context.

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?

With no annotations, no output schema, and 0% parameter description coverage, the description is incomplete for a two-parameter lookup tool. It does not explain parameter meaning, usage context, or expected return format, leaving the agent with insufficient information to call 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?

Schema description coverage is 0%, with two undocumented parameters (required 'name' and optional 'page'). The description adds no meaning for either parameter, leaving an agent unable to know what 'name' refers to or how pagination works.

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 names a verb ('Return') and a resource area ('semantic RPC observations and unresolved evidence limits'), so the general purpose is implied. However, 'semantic RPC observations' is vague and the phrase 'unresolved evidence limits' is unclear, so an agent cannot confidently distinguish this from siblings like get_thread_trace or get_unresolved.

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 when-to-use or when-not-to-use guidance, and no named alternatives despite many sibling tools. The description only states what is returned, leaving the agent with no routing context.

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