groups_reports_get_one

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

No annotations provided, so the description must carry the full behavioral burden. It only implies read-only via keywords ('read-only') but doesn't disclose authentication requirements, return format, access scope (group-level), or whether it requires specific permissions. Very thin for a get-by-ID 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?

The description is bloated with a long list of redundant synonyms and keywords that add no value. The core information ('Get report') is buried in repetitive boilerplate. Not front-loaded efficiently—the keyword spam dominates over substantive content.

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 simple get-by-ID tool with no output schema and no annotations, the description is insufficient. It doesn't explain what a report represents, what fields are returned, whether the item must belong to the caller's group, or error behavior. The keyword dump is filler, not contextual completeness.

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 0% (only type/format info, no description). The description doesn't explain what item_id refers to (report ID?) or its format beyond the UUID schema. With 1 param and partial schema info, the description should clarify it's the report's unique identifier but fails to.

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 ('Get') and resource ('report') with the REST endpoint path. The resource is clear enough to distinguish from siblings like groups_reports_get_all or groups_reports_delete_one. However, the description is somewhat redundant with the title/name and doesn't clarify what a 'report' contains in the Mealie context.

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?

No guidance on when to use this tool vs alternatives. The description doesn't mention prerequisites, when to prefer groups_reports_get_all for listing, or any usage context. Keywords list is just synonym padding, not usage guidance.

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