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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered, and the description adds real value by enumerating the payload sections (marsell_says, last_pass, needs_you, this_week, numbers, today) in the absence of an output schema. It also discloses an unusual side behavior: ask_the_owner surfaces cards only the owner can answer and asks the caller to tell the owner where the card is. What it does not disclose is cost/latency or how heavy the response is, which matters for a dashboard-shaped read.

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?

Purpose and the alternative-tool routing are front-loaded, but the middle is one long comma-chained sentence enumerating six payload sections, several of which use opaque internal jargon (marsell_says, last_pass, needs_you) with no gloss. It earns its place in content but loses clarity through density and awkward parallelism.

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 single-optional-parameter read tool with no output schema and no pagination concerns, the description covers purpose, contents, and alternative routes adequately. The remaining gap is that the enumerated section names are not defined in plain terms, so an agent knows a section exists but not precisely what it returns.

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 100% and the single optional project parameter is already documented as accepting id or exact name and being omittable for single-project accounts. The description adds no extra meaning about the project argument, so it sits at the baseline where the schema does the work.

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?

Opens with a specific verb and resource: "Reads where a project stands, as its Home shows it," which pins down both action and scope. It then names the sibling tools it is not (get_app, card_read, get_analytics), so an agent can distinguish it from the large set of read tools without inspecting schemas.

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?

"Use it for a quick daily look" states the intended occasion, and the same sentence routes three alternatives to their own tools: the whole app to get_app, a full card to card_read, full numbers to get_analytics. Both when-to-use and when-not-to-use are explicit.

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