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

With no annotations, the description carries the full burden and does disclose genuinely non-obvious behavior: the mapping method is advisory rather than prescriptive, and only sourced items may be treated as facts. That is valuable epistemic context an agent would otherwise guess wrong. It stops short of stating that the operation is read-only or that the project parameter is optional and what happens when it is omitted.

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?

Three short sentences with no padding, and the most important caveat (method is a suggestion) is placed early. The opening sentence is a fragment rather than a clause, which slightly weakens front-loading of what the tool actually does.

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?

There is no output schema, so the description must enumerate return content, and it does list the three components. However, for a tool with no annotations and an optional sole parameter, it omits the read-only nature and the behavior when project is absent, leaving real gaps for a composition tool that pulls several sibling data sources.

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 with 100% schema description coverage, so the schema already defines 'project'. The description references 'the user's project' but adds no syntax, scope, or fallback behavior beyond labeling it optional and suggesting how to phrase it. Baseline 3 applies when the schema does the documenting.

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 names the content the tool produces (today's brief, top curated wire items, a suggested mapping method), which makes the substance clear, but it is written as a noun-phrase inventory rather than a verb+resource statement of what the tool does. It also never states how it differs from get_daily_brief or get_wire, which appear to supply overlapping content, so an agent must infer the composition relationship.

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 when-to-use guidance and no named alternative; nothing says whether to call this instead of get_daily_brief plus get_wire, or when a bare brief is sufficient. The only guidance offered ('The method is a suggestion, not an instruction') is a consumption caveat, not a selection rule.

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