wordpress_get_template_parts

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

With no annotations provided, the description carries full burden. It indicates a read operation ('Get'), but doesn't disclose behavioral traits like whether it requires specific permissions, returns all template parts or a filtered subset, includes pagination, or provides error handling. The parenthetical adds some context about what template parts are, but lacks operational details.

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 a single, efficient sentence with a clear main clause and a helpful parenthetical elaboration. Every word earns its place, and it's front-loaded with the core purpose.

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 read-only tool with 0 parameters and no output schema, the description is minimally adequate. It states what the tool retrieves but lacks details on return format, scope, or behavioral context. Without annotations or output schema, more completeness would be beneficial, but it meets a basic threshold.

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?

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. Baseline for 0 parameters is 4.

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 clearly states the verb 'Get' and the resource 'theme template parts', with a helpful parenthetical explanation of what template parts are ('block theme components like header, footer'). It distinguishes from siblings by focusing on template parts, but doesn't explicitly differentiate from similar tools like 'wordpress_get_theme_templates' or 'wordpress_get_block_template'.

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 is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context, or compare it to sibling tools like 'wordpress_get_theme_templates' or 'wordpress_get_block_template' that might retrieve related theme components.

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