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

With no annotations, the description carries the behavioral burden and does well: it states only published projects are returned, ordering is newest first, category filtering is optional, and the return payload is described. It does not go into pagination, access requirements, or error behavior, but the core behavior of this read-only list is clear.

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 pack purpose, scope, return shape, ordering, filtering, and the onward path to get_project with no filler. The most important information is front-loaded.

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 list tool with only two simple parameters and no output schema, the description is complete: it explains what is returned, the order, the optional filter, and the next step for details. All invocation-relevant context is covered.

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 both parameters already have clear enum-based descriptions with defaults. The description adds only 'Optionally filter by category,' which restates the schema rather than adding new parameter semantics, so the baseline score of 3 is appropriate.

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 opens with the specific verb 'List' and a clear resource: Sofia Ferro's published projects, then enumerates the covered categories and the exact fields returned. It also names get_project as the sibling covering the next level of detail, so an agent can distinguish this tool from the other project-related tool.

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?

It gives an explicit alternative condition: use get_project with a slug when the full write-up is needed, implying list_projects is for overviews and discovery. It does not mention when not to use contact, get_manifesto, or get_resume, but those are clearly different resources.

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