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

With no annotations, the description carries the burden of behavioral disclosure. It describes the output fields, which is useful, but it does not explicitly state that this is a read-only operation, nor does it mention error handling or what happens if the idea does not exist. The term 'get' implies non-mutating behavior, but the description does not confirm it.

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 most important information (what is returned). It avoids unnecessary verbosity and is well-structured for a simple getter.

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?

Given the tool's simplicity (one required parameter, no output schema), the description is still incomplete. It does not explain the input parameter or the retrieval action, and it omits any mention of errors or edge cases. While it does list the returned fields, it lacks the contextual glue needed for an agent to invoke it correctly without inferring from the name.

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%, so the description must compensate. It does not mention the 'id' parameter at all, leaving the agent without any guidance on what the parameter means or how to provide it. Even though the name 'id' is self-explanatory, the description fails to connect it to the retrieval action.

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 indicates this tool returns a single idea with specific fields (text, status, decision, votes). It is distinguishable from list_ideas (which likely returns multiple ideas) and from mutation tools like comment_idea or vote_idea. However, it does not explicitly state it retrieves by ID, though the name 'get_idea' implies that.

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 guidance on when to use this tool versus alternatives. It does not mention that it is for fetching a specific idea by ID, nor does it contrast with list_ideas or other tools. The agent is left to infer usage from the name and schema.

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