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

With no annotations, the description does add two pieces of real behavioral context: a Bearer token is required, and results are scoped to the caller's private board. It says nothing about ordering, size limits, pagination, or what happens on an empty board, which is left entirely undisclosed for a zero-annotation 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?

Two short sentences, the resource statement first and the auth prerequisite second, with no filler or repetition of the tool name.

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 zero-parameter read with no output schema and no nested structures, the definition covers what it does and the auth requirement. The main remaining gap is the shape of the returned list, though with no parameters there is little an agent can get wrong before invoking it.

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 tool takes no parameters, so the baseline is 4. The description correctly implies no filtering or scoping inputs are needed because the board is implicitly the caller's own.

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?

'List the caller's private saved-homes board' pairs a specific verb with a specific resource and scopes it to the caller, which separates it from search_homes or get_home. It stops short of naming a sibling, so an agent must infer the boundary itself.

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?

Usage is only implied: 'the caller's private saved-homes board' suggests retrieving your own saved items rather than searching or fetching a single home. There is no explicit when-to-use statement, no mention of when board_save or board_update would be preferred, and no note on empty-board behavior.

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