Inspect Frontispice project status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by specifying exactly what is read (message counts, latest sequence, consumer cursors), which gives the agent additional context beyond the annotations. No contradictions exist.

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, concise sentence that front-loads the action ('Read') and immediately lists the specific data points. There is no fluff or irrelevant information, making it highly efficient.

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?

This is a simple read operation with one parameter, rich annotations, and no output schema. The description clearly states what information is returned (counts, sequence, cursors), which is sufficient for an agent to understand the tool's behavior. However, it lacks any mention of edge cases or how 'project' is referenced, so it is not maximally complete.

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 schema has one required parameter 'project' with 0% description coverage. The description implicitly indicates that the parameter identifies the project to inspect ('project message counts'), but it does not specify the expected format or provide examples. The bare name gives some semantics, so it is not a complete failure, but the description should compensate more for the schema's lack of detail.

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 uses a specific verb ('Read') and clearly identifies the resources: 'project message counts, latest sequence, and consumer cursors.' This distinguishes it from sibling tools like publish, route, or advance_cursor, which imply mutations or workflows. The title reinforces the inspection purpose.

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 provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or when a different sibling tool would be more appropriate. While the read-only nature implies inspection, there is no explicit usage context.

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