Get Tracker entity attachment

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint, so the safety profile is covered. The description adds real value beyond them by disclosing the exact metadata fields returned and a hard capability boundary (raw byte download is not available via MCP), which prevents a failed invocation.

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 primary purpose front-loaded, followed by the one important caveat. Every clause earns its place with no filler.

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?

With no output schema, the description carries the burden of describing the return content and does so by listing the metadata fields. It is complete enough to call correctly, though it could note auth/permission requirements for private attachments.

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%, so entity_type, entity_id, and file_id are already documented in the schema. The description adds no syntax or format detail beyond it, making 3 the correct 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?

States a specific verb and resource ('One attachment's metadata') and enumerates the returned fields (name, size, MIME type, download URL), so the agent knows exactly what this retrieves. It doesn't explicitly name its nearest sibling (tracker_entities_attachments_list or tracker_attachments_get) to disambiguate, so it falls short of a 5.

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?

The note that 'Downloading the raw bytes is CLI/SDK-only' usefully tells the agent what this tool cannot do, but there is no explicit statement of when to prefer this over the list/get variants. Usage is implied (fetch one known attachment id) rather than spelled out.

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