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

With no annotations, the description carries the full behavioral burden and does disclose the authorization model, which is the most important trait for this tool. It does not cover failure behavior (what happens when the caller is unauthorized or the id is unknown) or rate limits, so it is strong but not exhaustive.

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?

Two tightly written sentences, front-loaded with the action and payload, followed by the access rule. Nothing is redundant or padded.

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?

An output schema exists, so return values need not be explained, and the access model is covered. The remaining gap is error/unauthorized behavior, which an agent would benefit from knowing given the described permission rules.

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?

There is a single parameter ('id') with 100% schema description coverage, so the schema already documents it as the Dibs idea id. The description adds no format, example, or lookup guidance beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb and resource ('Fetch an idea') and adds the payload scope ('including match and settlement state'), which tells the agent this is a rich single-entity read rather than a summary. It is unmistakably distinct from the sibling list_my_ideas, list_repos, and submit_idea.

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 clearly states the access conditions: public ideas need no auth, private ideas require being the author or the owner of a repo with a pending/accepted offer. That is useful routing context, but it never explicitly contrasts this tool with alternatives (e.g., list_my_ideas for enumeration), so it falls short of a full when/when-not statement.

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