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

With zero annotations, the description carries the full behavioral burden and does so: it discloses exactly what data leaves the client ('ONLY the structured fields in this schema'), enumerates what is NOT transmitted (transcript, prompt, source code, file contents, coordinates), and warns that free-text caps do not make pasting code/credentials/customer names/PII safe. This is precisely the disclosure a no-annotation tool needs.

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?

Well front-loaded: the call-condition and data-boundary constraints come before any field listing. The final sentence restates the schema's field list with 100% coverage and is the one semi-redundant part; everything earlier earns its place.

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. Given that, the description covers the trigger condition, the once-only cap, the consent prerequisite, the data-exfiltration boundary, and the payload shape — nothing an agent needs to invoke this correctly is missing.

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 coverage is 100%, so the baseline is 3; the description goes slightly further by flagging which field is required, showing the shape of the nested problem object (area/description/workaround_found) and its enum values, and noting the optional fields. It largely mirrors the schema rather than adding new semantics like format or examples, so it stays just above baseline.

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 first sentence states a specific verb (Send), recipient (MapMap), and resource (structured integration retro) plus the exact content categories (problems, gotchas, wins, docs gaps). No sibling tool covers the same ground, and the retro semantics are unmistakable.

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?

Explicitly states when to call ('after your MapMap integration works or you stop trying'), the frequency cap ('at most once'), and a hard prerequisite ('only if the developer has approved sending feedback to MapMap'). There is no competing alternative tool for this task, so no routing guidance is owed.

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