updatePost

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

Discloses HTTP method (PUT) and replacement semantics, which is useful. However, with no annotations, it does not cover other behaviors like idempotency, side effects, error handling, or whether it returns the updated resource.

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?

Single concise sentence (10 words). Zero waste, effectively conveys the essential information.

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 simple update tool with well-documented parameters, the description is mostly complete. Lacks return value information (no output schema) but is sufficient for basic agent use.

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?

Both parameters have schema descriptions (100% coverage). The description adds no new information beyond reinforcing that 'updatedPostData' should be the complete object; thus baseline score of 3 is appropriate.

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?

Clearly states 'Updates an existing post using PUT (replaces the entire post)'. Action and resource are specific, and the replacement behavior distinguishes it from other CRUD operations like createPost or deletePost.

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?

Implied usage for updating existing posts, but no explicit guidance on when to use versus alternatives (e.g., when to use partial update or delete+create). No mention of prerequisites or context.

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